Bandwidth part operation during handover procedure

ABSTRACT

The present disclosure relates to a mobile terminal for performing a handover procedure in a mobile communication system from a source to a target base station. The target base station is configured for the mobile terminal with at least a first and a different second bandwidth part within its cell bandwidth. The mobile terminal comprises: a transceiver which, in operation, receives from the source base station a handover command message including information regarding the configured at least first and second bandwidth part; and a processor which, in operation and upon reception of the handover command message, activates in the transceiver at least a selected one of the configured at least first or second bandwidth part, and controls the transceiver to perform, over the activated at least one of the configured at least first or second bandwidth part, communication with the target base station as part of the handover procedure.

TECHNICAL FIELD

The present disclosure relates to a mobile terminal performing ahandover procedure in a wireless communication system from a source basestation to a target base station.

DESCRIPTION OF THE RELATED ART

Currently, the 3^(rd) Generation Partnership Project (3GPP) focuses onthe next release (Release 15) of technical specifications for the nextgeneration cellular technology, which is also called fifth generation(5G).

At the 3GPP Technical Specification Group (TSG) Radio Access network(RAN) meeting #71 (Gothenburg, March 2016), the first 5G study item,“Study on New Radio Access Technology” involving RAN1, RAN2, RAN3 andRAN4 was approved and the study has laid the foundation of the Release15 work item (WI) which will define the first 5G standard.

5G new radio (NR) provides a single technical framework addressing allusage scenarios, requirements and deployment scenarios defined in 3GPPTSG RAN TR 38.913 v14.1.0, “Study on Scenarios and Requirements for NextGeneration Access Technologies”, Dec. 2016 (available at www.3gpp.org),at least including enhanced mobile broadband (eMBB), ultra-reliablelow-latency communications (URLLC), massive machine type communication(mMTC).

For example, eMBB deployment scenarios may include indoor hotspot, denseurban, rural, urban macro and high speed; URLLC deployment scenarios mayinclude industrial control systems, mobile health care (remotemonitoring, diagnosis and treatment), real time control of vehicles,wide area monitoring and control systems for smart grids; mMTC mayinclude the scenarios with large number of devices with non-timecritical data transfers such as smart wearables and sensor networks.

The forward compatibility, anticipating future use cases/deploymentscenarios are also provided in 5G. The backward compatibility to LongTerm Evolution (LTE) is not required, which facilitates a completely newsystem design and/or the introduction of novel features.

As summarized in one of the technical reports for the NR study item(3GPP TSG TR 38.801 v2.0.0, “Study on New Radio Access Technology; RadioAccess Architecture and Interfaces”, March 2017), the fundamentalphysical layer signal waveform will be based on Orthogonal FrequencyDivision Multiplexing (OFDM). For both downlink and uplink, OFDM withcyclic prefix (CP-OFDM) based waveform is supported. Discrete FourierTransformation (DFT) spread OFDM (DFT-S-OFDM) based waveform is alsosupported, complementary to CP-OFDM waveform at least for eMBB uplinkfor up to 40 GHz.

One of the design targets in NR is to enhance the user's mobility withminimizing the interruption of ongoing traffic if any, and at the sametime without increasing the user equipment power consumption. At RAN#78, RAN2 was tasked to investigate how the IMT-2020 requirement on Omshandover interruption time can be addressed for LTE and NR within theRel-15 time frame. At a first step, handover procedure in LTE has beendiscussed as a baseline design in NR. There are ongoing discussions in3gpp working groups regarding what functionalities need to be added ormodified for NR mobility enhancement.

The term “downlink” refers to communication from a higher node to alower node (e.g., from a base station to a relay node or to a UE, from arelay node to a UE, or the like). The term “uplink” refers tocommunication from a lower node to the higher node (e.g., from a UE to arelay node or to a base station, from a relay node to a base station, orthe like). The term “sidelink” refers to communication between nodes atthe same level (e.g., between two UEs, or between two relay nodes, orbetween two base stations).

BRIEF SUMMARY

One non-limiting and exemplary embodiment enables the mobile terminal tomore quickly perform handover from a source base station to a targetbase station. When the target base station already during handoverconfigures plural bandwidth parts for the mobile terminal and signalingsame configurations to the mobile terminal, the mobile terminal caninstantaneously start communicating (again) during the handover over asuitable bandwidth part configuration with the target base station.After handover, additional reconfiguration attempts may be avoided.

In an embodiment, the techniques disclosed here feature a mobileterminal for performing a handover procedure in a mobile communicationsystem from a source base station to a target base station. The targetbase station is configured for the mobile terminal with at least a firstbandwidth part and a different second bandwidth part within its cellbandwidth. The mobile terminal comprises: a transceiver which, inoperation, receives from the source base station a handover commandmessage including information regarding the configured at least firstbandwidth part and second bandwidth part; and processing circuitry, suchas a processor which, in operation and upon reception of the handovercommand message, activates in the transceiver at least a pre-selectedone of the configured at least first bandwidth part or second bandwidthpart, and controls the transceiver to perform, over the activated atleast one of the configured at least first bandwidth part or secondbandwidth part, communication with the target base station as part ofthe handover procedure.

In another general aspect, the techniques disclosed here feature amobile terminal for performing a handover procedure in a mobilecommunication system from a source base station to a target basestation. The target base station is configured for the mobile terminalwith at least a first bandwidth part and a different second bandwidthpart within its cell bandwidth. The mobile terminal comprises: atransceiver which, in operation, receives from the source base station ahandover command message including information regarding the configuredat least first bandwidth part and second bandwidth part; and a processorwhich, in operation and upon reception of the handover command message,selects and activates in the transceiver at least one of the configuredat least first bandwidth part or the second bandwidth part, and controlsthe transceiver to perform, over the selected and activated at least oneof the configured at least first bandwidth part or the second bandwidthpart, communication with the target base station as part of the handoverprocedure.

In further general aspect, the techniques disclosed here feature atarget base station for performing a handover procedure of a mobileterminal in a mobile communication system from a source base station.The target base station is capable of communicating with the mobileterminal over each of at least a first bandwidth part and a differentsecond bandwidth part within its cell bandwidth. The target base stationcomprises: a transceiver which, in operation, receives from the sourcebase station a handover request message including information regardingthe capability of the mobile terminal to communicate over at least thefirst bandwidth part and second bandwidth part; and a processor which,in operation and upon reception of the handover request message,controls the transceiver to configure for the mobile terminal at leastthe first bandwidth part and the second bandwidth part, and controls thetransceiver to transmits to the source base station a handover requestacknowledge message, wherein the handover request acknowledge messageincludes information regarding the configured at least first bandwidthpart and second bandwidth part.

In yet another general aspect, the techniques disclosed here feature amethod for performing a handover procedure of a mobile terminal in amobile communication system from a source base station to a target basestation. The target base station is configured for the mobile terminalwith at least a first bandwidth part and a different second bandwidthpart within its cell bandwidth. The method comprises the steps of:receiving from the source base station a handover command messageincluding information regarding the configured at least first bandwidthpart and second bandwidth part; and upon reception of the handovercommand message, activating at least a pre-selected one of theconfigured at least first bandwidth part or second bandwidth part, andcommunicating, over the activated at least one of the configured atleast first bandwidth part or second bandwidth part, with the targetbase station as part of the handover procedure.

In an even further general aspect, the techniques disclosed here featureanother method for performing a handover procedure of a mobile terminalin a mobile communication system from a source base station to a targetbase station. The target base station is configured for the mobileterminal with at least a first bandwidth part and a different secondbandwidth part within its cell bandwidth. The method comprises the stepsof: receiving from the source base station a handover command messageincluding information regarding the configured at least first bandwidthpart and second bandwidth part; and upon reception of the handovercommand message, selecting and activating at least one of the configuredat least first bandwidth part or the second bandwidth part, andcommunicating, over the selected and activated at least one of theconfigured at least first bandwidth part or the second bandwidth part,with the target base station as part of the handover procedure.

In yet another general aspect, the techniques disclosed here feature afurther method for a target base station to perform a handover procedureof a mobile terminal in a mobile communication system from a source basestation The target base station being capable of communicating with themobile terminal over each of at least a first bandwidth part and adifferent second bandwidth part within its cell bandwidth. The methodcomprises the steps of: receiving from the source base station ahandover request message including information regarding the capabilityof the mobile terminal to communicate over at least the first bandwidthpart and second bandwidth part; and upon reception of the handoverrequest message, configuring for the mobile terminal at least the firstbandwidth part and the second bandwidth part, and transmitting to thesource base station a handover request acknowledge message, wherein thehandover request acknowledge message includes information regarding theconfigured at least first bandwidth part and second bandwidth part.

It should be noted that general or specific embodiments may beimplemented as a system, a method, an integrated circuit, a computerprogram, a storage medium, or any selective combination thereof.

Additional benefits and advantages of the disclosed embodiments will beapparent from the specification and Figures. The benefits and/oradvantages may be individually obtained by the various embodiments andfeatures of the specification and drawings, which need not all beprovided in order to obtain one or more of such benefits and/oradvantages.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIGS. 1A and 1B show a sequence diagram of an exemplary handoverprocedure, and a scenario explaining bandwidth adaptation over time;

FIGS. 2A and 2B illustrate exemplary scenarios with bandwidth partconfigurations in a source and target cell before and after handover;

FIG. 3 is a block diagram showing the structure of a mobile terminal, asource and a target base station;

FIG. 4 depicts a sequence diagram of a handover procedure according toan exemplary implementation of the first embodiment in a 3GPP NRdeployment scenario;

FIG. 5 illustrates a sequence diagram of a handover procedure accordingto a different exemplary implementation of the first embodiment in a3GPP NR deployment scenario;

FIG. 6 depicts a sequence diagram of a handover procedure according toan exemplary implementation of the second embodiment in a 3GPP NRdeployment scenario;

FIG. 7 show an association table for the handover procedure according toFIG. 6 ;

FIG. 8 illustrates a sequence diagram of a handover procedure accordingto a different exemplary implementation of the second embodiment in a3GPP NR deployment scenario; and

FIG. 9 show another association table for the handover procedureaccording to FIG. 8 .

DETAILED DESCRIPTION

In 3GPP NR, bandwidth part (BWP) operation is introduced as a newfeature. A BWP of a group of contiguous physical resource blocks (PRBs).It defines the UE's operating bandwidth within the cell's operatingbandwidth. Furthermore, the bandwidth of a BWP equals to or is smallerthan the maximal bandwidth capability supported by a UE.

For each UE-specific serving cell, one or more downlink BWPs and one ormore uplink BWPs can be configured by dedicated radio resource control,RRC, signaling for a UE. The configuration of a BWP may include thefollowing properties: Numerology, frequency location (e.g., centerfrequency), and bandwidth (e.g., number of PRBs), where the numerologymeans the subcarrier spacing and the cyclic prefix.

However, in Release-15, for a UE, there is at most one active downlinkBWP and at most one active uplink BWP at a given time for a servingcell. A UE only expects the communication from/to gNB via the activeBWPs, meaning that the UE may monitor only the active downlink BWP forPDCCH and possible PDSCH, and may transmit PUSCH/PUCCH only in theactive uplink BWP.

NR supports the case that a single scheduling DCI (downlink controlinformation) can switch the UE's active BWP from one to another amongthe BWPs that have been configured for the UE. This is referred to as(dynamic) BWP adaptation.

Bandwidth adaptation is described in the 3GPP technical specification toNew Radio, NR, and Next Generation, NG,-Radio Access Network, RAN, (3GPPTSG TS 38.300 V.2.0.0, “NR; NR and NG-RAN Overall Description”, December2017) as follows:

With Bandwidth Adaptation (BA), the receive and transmit bandwidth of aUE need not be as large as the bandwidth of the cell and can beadjusted: the width can be ordered to change (e.g., to shrink duringperiod of low activity to save power); the location can move in thefrequency domain (e.g., to increase scheduling flexibility); and thesubcarrier spacing can be ordered to change (e.g., to allow differentservices). A subset of the total cell bandwidth of a cell is referred toas a Bandwidth Part (BWP) and BA is achieved by configuring the UE withBWP(s) and telling the UE which of the configured BWPs is currently theactive one.

It is possible to conceive a scenario where 3 different BWPs areconfigured as shown in FIG. 1B, each having same or different centerfrequency, different (band-) width and/or different subcarrier spacing:

-   -   BWP1 with a width of 40 MHz and subcarrier spacing of 15 kHz;    -   BWP2 with a width of 10 MHz and subcarrier spacing of 15 kHz;        and    -   BWP3 with a width of 20 MHz and subcarrier spacing of 60 kHz.

A general description of network controlled mobility is given in the3GPP technical specification to New Radio, NR, and Next Generation,NG,-Radio Access Network, RAN, (3GPP TSG TS 38.300 V.2.0.0, “NR; NR andNG-RAN Overall Description”, December 2017). Network controlled mobilityapplies to UEs in RRC_CONNECTED and is categorized into two types ofmobility: cell level mobility and beam level mobility.

Cell Level Mobility requires explicit RRC signaling to be triggered,e.g., handover. For inter-gNB handover, the signaling procedures includeat least the following elemental components illustrated in FIG. 9.2.3.1-1, which is reproduced herein as FIG. 1A for consistency reasons.Separate therefrom, Beam Level Mobility does not require explicit RRCsignaling to be triggered—it is dealt with at lower layers—and RRC isnot required to know which beam is being used at a given point in time.

As shown in FIG. 1A, the RRC driven mobility is responsible for the celllevel mobility, e.g., handover. Handover signaling procedures adopt thesame principle as Rel-13 LTE. For inter-gNB handover, the signalingprocedures consist of at least the following elemental components.

-   -   1. The source gNB initiates handover and issues a Handover        Request over the Xn interface.    -   2. The target gNB performs admission control and provides the        RRC configuration as part of the Handover Acknowledgement.    -   3. The source gNB provides the RRC configuration to the UE in        the Handover Command. The Handover Command message includes at        least cell ID and information required to access the target cell        so that the UE can access the target cell without reading system        information. For some cases, the information required for        contention based and contention free random access can be        included in the Handover Command message. The access information        to the target cell may include beam specific information, if        any.    -   4. The UE moves the RRC connection to the target gNB and replies        the Handover Complete.

The handover mechanism triggered by RRC requires the UE at least toreset the MAC entity and re-establish RLC. RRC managed handovers withand without PDCP entity re-establishment are both supported. For DRBsusing RLC AM mode, PDCP can either be re-established together with asecurity key change or initiate a data recovery procedure without a keychange. For DRBs using RLC UM mode and for SRBs, PDCP can either bere-established together with a security key change or remain as it iswithout a key change.

Data forwarding, in-sequence delivery and duplication avoidance athandover can be facilitated when the target gNB uses the same DRBconfiguration and QoS flow to DRB mapping as the source gNB. Timer basedhandover failure procedure is supported in NR. RRC connectionre-establishment procedure is used for recovering from handover failure.

It shall be mentioned that the elemental components illustrated in FIG.1A not only characterize the inter-gNB handover but are also part of theintra-NR RAN Handover. For reasons of brevity, reference is made to FIG.9.2 .3.2.1-1 disclosing particular aspects to an intra-AMF/UPF handover.In this figure, the Handover Request is in message 3, the Handover(Request) Acknowledge is in message 5, the Handover Command is part ofthe communication 6 and the Handover Complete is part of thecommunication 8.

Importantly, the elemental components of the presently known handover donot support the concept of bandwidth adaptation. Recognizing theseshortcomings the present disclosure strives to improve the handoverprocedure.

Non-limiting and exemplary embodiments facilitate the mobile terminal tomore quickly perform handover from a source base station to a targetbase station and minimize the interruption of the ongoing datatransmission (if any) and avoiding increasing the mobile terminal powerconsumption.

When the target base station already during handover configures pluralbandwidth parts for the mobile terminal and signaling sameconfigurations to the mobile terminal, the mobile terminal caninstantaneously start communicating (again) during the handover over asuitable bandwidth part configuration with the target base station.After handover, additional reconfiguration or bandwidth part adaptationattempts may no longer be necessary.

It shall be mentioned that the Xn interface for inter-gNB messageexchange is chosen for the purpose of illustration of the currentdisclosure. It should not be regarded as the limitation of the currentdisclosure, which can be applied in a straightforward way tointer-AMF/UPF handover case where the information regarding bandwidthpart usage mentioned in this disclosure would be exchange via theinterface between gNB and core network.

For a more comprehensive discussion of the advantages provided by thepresent disclosure, two different scenarios shall be described infurther detail. From this description it shall become apparent thatthere are further synergistic effects which can be achieved whenconsidering bandwidth adaptation at the handover.

Referring to FIG. 2A, an exemplary scenario is shown where a mobileterminal is configured with plural bandwidth parts in the source andtarget cell, e.g., before and after handover.

This exemplary scenario depicts a situation where the mobile terminalperforms a handover from a source base station (more specifically fromthe source cell which is served by the source base station) to thetarget base station (more specifically in the target cell which isserved by the target base station). In both, the source cell and thetarget cell the mobile terminal is configured with plural bandwidthparts, e.g., a first and a second bandwidth part with correspondingindexes #0 and #1.

Particularly, in the source cell and the target cell the configuration(e.g., location and bandwidth) of the first bandwidth part (referred toas BWP with index #0) and the second bandwidth part (referred to as BWPwith index #1) is shown with regard to the Synchronization Signal, SS,block in the carrier bandwidth, e.g., in the frequency domain.

As the indicated first and second bandwidth parts are included in thesame carrier bandwidth also occupied by the SS block, they bothcorrespond to downlink bandwidth parts for the mobile terminal. Thefurther description, however, equally applies for uplink bandwidth partsuch that a specific distinction has been omitted for reasons ofsimplicity.

In the source cell, the first and second bandwidth parts are bothconfigured in central alignment (in frequency domain) with one (e.g.,the lower) SS block, and in the target cell, the first and secondbandwidth parts are both configured in central alignment (in frequencydomain) with another (e.g., the upper) SS block. In other words, in thisexemplary scenario the plural bandwidth parts are located in differentparts of the carrier frequency.

Accordingly, when a mobile terminal is triggered to perform handoverfrom the source cell to the target cell, it receives radio resourcesfrom a different part of the carrier bandwidth. This is beneficial forthe load balancing purpose in the target cell.

However, the adaptation of the reception operation in a mobile terminalincludes (re-)tuning to a different center frequency where therespective bandwidth part is located and adjusting the filteringbandwidth to the corresponding (band-) width of the Referring to FIG.2B, another exemplary scenario is shown where a mobile terminal is(again) configured with plural bandwidth parts in the source and targetcell, e.g., before and after handover.

Now, in the source cell as well as in the target cell the first andsecond bandwidth parts are no longer configured in central alignment (infrequency domain) with one or another SS block, but instead they aremore flexibly distributed over in the carrier bandwidth. Importantly,the mobile terminal is configured with a first bandwidth part in thesource cell and in the target cell which are at a same location and havea same (band-) width (e.g., in number of physical resource blocks,PRBs).

Accordingly, when the mobile terminal is triggered to perform handoverfrom the first bandwidth part (BWP #0) in the source cell to the firstbandwidth part (BWP #0) in the target cell, it does not have to receiveradio resources from a different part of the carrier bandwidth. Instead,the reception operation in the mobile terminal can stay the same.

This other exemplary scenario does not require the (re-)tuning and thefilter adaptation to be carried out, such that the interruption ofongoing traffic due to frequency retuning during handover is avoided.

It shall however not go without saying that in this other exemplaryscenario the mobile terminal is configured with second bandwidth parts(BWP #1) in the source cell and in the target cell which are notcentrally aligned (in frequency domain) with the respective firstbandwidth parts (BWP #0). When changing between the different bandwidthparts, the mobile terminal receives radio resources from a differentparts of the carrier bandwidth.

In other words, changing between the first and the second bandwidth partwithin each of the source and target cell will require both the(re-)tuning and the filter adaptation to be carried out, such that thechange is delayed (increasing latency). This may however be compensatedwith the increased bandwidth the mobile terminal can utilize in thesecond bandwidth part (BWP #1) of the source and target cell.

In summary, two different exemplary scenarios are discussed where thelater (shown in FIG. 2 b ) has the advantage that it permits seamlesshandovers at least between the first bandwidth parts in the source celland the target cell and the former can achieve the load balancing (shownin FIG. 2 a ).

These considerations are not restricted to downlink bandwidth parts butalso apply to the uplink bandwidth parts in a source cell or a targetcell. Also for uplink bandwidth parts the location and width is decisivefor the transmission operation in the mobile terminal. The mobileterminal may be required to carry out uplink transmission on differentfrequency resources which usually also requires (re-)tuning and thefilter adaptation.

Thus, the above discussed advantages/disadvantages equally apply fordownlink bandwidth parts as well as uplink bandwidth parts.

FIG. 3 illustrates a block diagram of mobile communication systemincluding a mobile terminal 100 (also referred to as user equipment,UE), a source base station 200-a (also referred to as source g Node B,gNB) and a target base station 200-b (also referred to as target g NodeB, gNB). This block diagram serves the purpose of showing the mobileterminal in a situation where it performs a handover from the sourcebase station 200-a to the target base station 200-b.

In general, there exist multiple events that can cause a source basestation 200-a to trigger the handover of the mobile terminal 100. Forexample, the source base station 200-a may trigger the handover due toan inferior coverage situation of the mobile terminal 100. The coverageis measured by the mobile terminal 100 in form of measurements and(subsequently) reported to the source base station 200-a. Alternatively,the source base station 200-a may also trigger handover of a mobileterminal 100, due to load balancing reasons in the source base station200-a.

Regardless of what the cause may be, a processor 230-a of the sourcebase station 200-a triggers handover to a target base station 200-b bycausing its transceiver 220-a to transmit a handover request message(see message 1 in FIG. 1 ) to the target base station 200-b.

This and other messages may be sent over a wireless or wired interfaceconnecting the base stations with each other. For example, the handoverrequest message may be transmitted over the Xn interface which isdefined as part of the Next Generation, NG, Radio Access Network, RAN,or over the Next Generation, NG, interface via the entity providing theAccess and Mobility Management Function, AMF, and/or the User PlaneFunction, UPF. If the handover involves different 5G core networks, itmay even be necessary to forward same message between different AMF/PDFentities.

A transceiver 220-b of the target base station 200-b receives from thesource base station 200-a the handover request message. Particular, thismessage includes (among others) information regarding the capability ofthe mobile terminal 100 to communicate over at least two differentbandwidth parts, e.g., a first bandwidth part BWP #0 and a secondbandwidth part BWP #1 in the uplink and downlink. This informationassists the target base station 200-b in deciding how many bandwidthparts it is expected to configured for the mobile terminal 100.

Assuming for the sake of example that the mobile terminal 100 is onlycapable of communicating over a single and not plural bandwidth parts,then the target base station 200-b will refrain from configuring morethan one bandwidth part for the mobile terminal 100. Despite thispossibility, the present disclosure focuses on mobile terminals 100which are capable of communicating over plural bandwidth parts, thuspromoting the target base station 200-b to configure all of the pluralbandwidth parts for the mobile terminal.

The above restriction on bandwidth part capabilities may be understoodas equally applying to the uplink and downlink in frequency divisionduplex, FDD, operation mode, as well as to the uplink and downlink intime division duplex, TDD, operation mode.

In other words, if a mobile terminal is said to be capable ofcommunicating over a single bandwidth part in the FDD operation mode,then this may be understood as implying a configuration with at most asingle bandwidth part in the downlink and a separate single bandwidthpart in the uplink. If a mobile terminal is said to be capable ofcommunication over a single bandwidth part in the TDD operation mode,then this may be understood as implying a joint configuration with(also) at most a single bandwidth part in the downlink and a singlebandwidth part in the uplink (as a pair).

For this reasons, the present disclosure is laid out to refer to term“bandwidth parts”, knowing that reference could equally be made to theterm “uplink and downlink bandwidth parts” or even “uplink and downlinkbandwidth part pairs”. Both cases merely emphasize, e.g., that aseparate bandwidth part is necessarily configured in uplink anddownlink. Accordingly, it is indispensable for FDD and TDD operation toconfigure a first or second uplink and downlink bandwidth part, at thesame time.

When the target base station 200-b has received a handover requestmessage indicating that the mobile terminal 100 is capable ofcommunicating over at least two, e.g., a first and a second bandwidthpart in uplink and downlink, then the processor 230-b controls thetransceiver 220-b to configure for the mobile terminal both of the atleast first bandwidth part and the second bandwidth part.

Also the processor 230-b in the target base station 200-b controls thetransceiver 220-b to transmit a handover (request) acknowledge message(see message 2 in FIG. 1 ) to the source base station 200-a includinginformation regarding both, the configured at least first and secondbandwidth parts in uplink and in downlink.

For example, this information includes for each of the bandwidth partsin uplink and downlink a location (e.g., center frequency), a bandwidth(e.g., number of physical resource blocks, PRBs), a numerologyindicating the subcarrier spacing and cyclic prefix, and an indexassociated with this bandwidth.

Alternatively to the location, the information may also include anoffset which indirectly identifies the location of an uplink bandwidthpart by specifying the offset from a (given) location of a downlinkbandwidth part, or the offset from a known reference location, e.g., thefirst PRB of the DL carrier bandwidth. It may be mentioned that someparameters for the bandwidth part configuration, e.g., the location andthe bandwidth, can be encoded together to become a single parameter inthe configuration.

Again, this handover request acknowledge message may be sent via Xninterface connecting the base stations directly with each other or NGinterface connecting base station to core network.

The source base station 200-a then forwards the information from thishandover (request) acknowledge message to the mobile terminal 100. Thisinformation is conveyed in form of a handover command message (seemessage 3 in FIG. 1 ). In other words, at least the informationregarding the at least first bandwidth part and second bandwidth partconfigured in the target base station 200-b is (also) included in thehandover command message to the mobile terminal 100.

A transceiver 120 of the mobile terminal 100 receives the handovercommand message from the source base station 200-a which includes amongothers the (above mentioned) information regarding the configuredbandwidth parts. When receiving this handover command message, theprocessor 130 can process the included information in the presentdisclosure in two different mechanisms, which are discussed in thefollowing as first embodiment and second embodiment.

Separate from the details, it is important to understand that in bothembodiments the processor 130 of the mobile terminal 100 succeeds inactivating one of the bandwidth parts which have been configured(specifically) for this mobile terminal 100 and with this configuredbandwidth parts can already perform handover. Hence, the mobilecommunication system is not limited to perform handover with a commonconfiguration of bandwidth parts which are, for example, broadcasted toall mobile terminals via system information messages. With the methoddisclosed, the congestion in the common configured bandwidth part may beavoided.

In the first embodiment, the mobile terminal 100 processes theinformation in the handover command in such a manner that the processor130 activates in the transceiver 120 at least one pre-selected of theconfigured at least first and second bandwidth part in the uplink anddownlink. For example, the mobile terminal 100 activates (exactly) onepre-selected bandwidth part in the uplink and one pre-selected bandwidthpart in the downlink. However, this shall not be understood as alimitation in any respect. Rather, the mobile terminal 100 may alsoactivate more than one pre-selected bandwidth part in the uplink anddownlink. In future, to support simultaneous multi-numerologyprocessing, it may be beneficial for a mobile terminal to activate, inthe uplink and downlink carrier bandwidth, two bandwidth parts withdifferent numerologies at a same time. Thus, it can be said that themobile terminal 100 activates at least a pre-selected one of theconfigured bandwidth parts.

In the context of the present disclosure, the term “pre-selected” shallbe understood as emphasizing that the selection is not performed by themobile terminal itself. The selection can be defined by thespecifications as the bandwidth part with a specific index (e.g., index#0), or a special bandwidth part such as the initial bandwidth part orthe default bandwidth part, the selection is done by the target basestation and then indicated to the mobile terminal.

Having activated the at least one pre-selected bandwidth part, theprocessor 130 of the mobile terminal 100 controls the transceiver 120 toperform over the activated at least one pre-selected bandwidth partcommunication with the target base station 200-b as part of thehandover.

Since the target base station 200-b equally knows which one of theconfigured at least two bandwidth parts is the pre-selected one themobile terminal will activate, it can also proceed with activating,after having transmitted the handover (request) acknowledge message, thesame pre-selected at least one bandwidth part, the mobile terminal isexpected to activate.

In the first embodiment, the mobile terminal 100 is provided withinformation regarding the configured at least two bandwidth parts. Thisinformation is signaled to the mobile terminal 100 even though (only)one of the at least two bandwidth parts is already pre-selected. Despitethe (added) payload to the handover command, this informationadvantageously increases the flexibility at handover, namely permitting(already) at handover the switching between the configured at least twobandwidth parts.

Conversely, in the second embodiment, the mobile terminal 100 processesthe information in the handover command in such a manner that theprocessor 130 first (actively) selects and then activates in thetransceiver 130 at least one of the at least two configured bandwidthparts in the uplink and downlink. For example, also here the mobileterminal 100 selects and activates (exactly) one of the at least twobandwidth parts.

Again, this should not be understood as a limitation in any respect.Rather the mobile terminal 100 may also select and activate more thanone of the at least two configured bandwidth parts in the uplink anddownlink. This may yet again serves the purpose of processing multiplenumerologies simultaneously or mitigating congestion among the availableradio resource, for example, when selecting and activating twonon-contiguous bandwidth parts with different numerologies at a sametime.

Having selected and activated the at least one of the at least twoconfigured bandwidth parts in the uplink and downlink, the processor 130of the mobile terminal 100 controls the transceiver 120 to perform overthe selected and activated bandwidth parts communication with the targetbase station 200-b as part of the handover.

Here, the target base station 200-b does not know (exactly) which of theconfigured at least two bandwidth parts is being selected and activatedby the mobile terminal 100. Nevertheless, as both the at least twobandwidth parts are configured (specifically) for the mobile terminal tobe selected and activated, it can proceed with activating all of theconfigured at least two bandwidth parts and resolve this uncertainty atthe very initial phase to communicate with the mobile terminal.

Then at a later stage, as will be detailed next, the mobile terminal cannotify the selection of the first activated bandwidth to the target basestation by the method of RACH resource or PUSCH resourcedifferentiation.

As a result, the target base station 200-b may detect from the furthercommunication with the mobile terminal 100 which one of the configuredbandwidth parts is actually used for communication. Thereby, it canobtain (retroactively) the information which one of the configuredbandwidth parts the mobile terminal has selected and activated.

Also here it is important to recognize that, in the second embodiment,the mobile terminal 100 is provided with information regarding theconfigured at least two bandwidth parts. This information is signaled(together with other information detailed later) to the mobile terminal100 to enable the mobile terminal to make the selection and thenindicate the selection to the target base station.

Despite the (added) payload to the handover command, this informationadvantageously increases the flexibility at handover, namely permitting(already) at handover the switching between the configured at least twobandwidth parts.

FIG. 4 depicts a sequence diagram of a handover procedure according toan exemplary implementation of the first embodiment in a 3GPP NRdeployment scenario. In particular, a user equipment, UE, is shown whenperforming a handover from a source g Node B, gNB, to a target gNB.

In preparation of the handover, the source gNB transmits a handoverrequest message (see message 1 in FIG. 4 ) to the target gNB. Thehandover request message is usually transmitted over the Xn interfaceestablishing communication between gNBs in the next generation, NG,radio access network, RAN. This handover request message providessufficient details for the target gNB to prepare for the handover of theUE, e.g., perform admission control.

Via this handover request message, the target gNB receives informationregarding the capability of the UE to communicate over at least twobandwidth parts in uplink and downlink. This enables the target gNB toconfigure an appropriate number of bandwidth parts for the UE, e.g.,that meet the capability of the UE. For example, if the UE is capable ofcommunicating over two, a narrow and a wide bandwidth part, the targetgNB does well in configuring also two bandwidth parts for the UE.

Having configured the appropriate number of bandwidth parts in theuplink and downlink, the target gNB includes information thereon in thehandover (request) acknowledge message (see message 2 in FIG. 4 ). Thismessage is transmitted from the target gNB to the source gNB. Thehandover (request) acknowledge message is usually also transmitted overthe Xn interface if such interface between gNBs is available.

Successively, the source gNB relays the information in a handovercommand message (see message 3 in FIG. 4 ) to the UE. Thus, theinformation regarding the configured bandwidth parts in appropriatenumber is received by the UE. As discussed with regard to 3GPP NR, thehandover command message includes numerous details for the UE to performhandover to the target gNB.

Importantly, with the information on the (appropriate number of)configured bandwidth parts, the UE is put in a situation where it canperform a handover to the target gNB utilizing bandwidth parts whichhave been configured in a UE-specific manner for the UE. In other words,the UE is not restricted to performing handover on a (common) initialbandwidth part which is shared among numerous UEs at a time.

Thus, the information on configured bandwidth parts alleviatescongestion effects during handover, while at the same time thisinformation dispenses with the necessity of configuring bandwidth partsat a later point in time. These advantages are achieved irrespective ofthe fixed handover sequence with the limited number of messagesexchanged.

Advantageously, the UE with the target gNB can already perform therandom access message transmissions, in a random access channel, RACH,based handover, over the UE-specifically configured bandwidth partswithout necessity to rely on the (common) initial bandwidth part only.

Specifically, with the UE-specifically configured bandwidth parts, thereis less congestion for the RACH message 1, and the RACH message 2 can bemore flexibly scheduled.

The UE concludes the handover by transmitting a handover completemessage (see message 4—FIG. 4 ) to the target gNB.

Having elaborated on the different configurations of bandwidth parts foran UE, the discussion has so far been silent about which of pluralbandwidth parts is activated. This is an important point to mention asthe UE and also the target gNB (most likely) will not activate all theconfigured bandwidth parts in uplink and one in downlink, becauseactivating more bandwidth increases the power consumption and theprocessing complexity as well This is the reason in Release-15, it hasbeen agreed that NR mobile terminal activates a single downlinkbandwidth part and a single uplink bandwidth part at any given time.

Therefore, during handover the UE and the target gNB will activate onlyone of the configured bandwidth parts in the uplink and one in thedownlink. Thus, it is necessary to establish a common understandingbetween the target gNB and UE which one of the two configured bandwidthparts in both the uplink and downlink is to be activated.

In this exemplary implementation, it is assumed that from among theinformation regarding the configured bandwidth parts, there is (always)one pre-selected bandwidth part in the uplink and downlink which isactivated.

For example, assuming the information regarding the configured bandwidthparts have a specific sequence, then the UE as well as the target gNBcan (always) activate the first or the last bandwidth part in thespecific sequence. If there are more than two configured bandwidth partsin the sequence, then the UE as well as the target gNB can also (always)activate another one, say second, third, . . . , in the specificsequence.

As another example, the pre-selected bandwidth part can be some specialbandwidth part, e.g., the initial BWP or the default BWP. By providingnew configurations in the target gNB of such special BWP, the loadbalancing in the target cell can also be adapted.

In summary, the mere fact that the information regarding the configuredbandwidth parts is provided in a specific sequence suffices to establisha common understanding between the UE and target gNB which one from thissequence is to be activated.

For this, it is however necessary that the sequence in the informationregarding the configured bandwidth parts is the same in the handover(request) acknowledge message as well as in the handover command. Inother words, the source gNB relaying this information preserves thesequence of the information when generating from the handover (request)acknowledge message the handover command.

In an exemplary extension of this implementation, the handover (request)acknowledge message as well as the handover command also include randomaccess transmission parameters, such as a preamble sequence or a timeand frequency resource to be used during the RACH based handover.

Importantly, the included random access transmission parameters need tobe associated with at least the pre-selected one of the configuredbandwidth parts. Thus, the UE performs a random access messagetransmission (e.g., RACH message 1) using the random access transmissionparameters (specifically) associated with the pre-selected bandwidthpart to be activated.

Due to the freedom in defining the random access transmission parametersonly in association with the pre-selected one of the configuredbandwidth parts, the utilization of the RACH resources can be improved.In such case, target gNB does not need to reserve the RACH resourcescorresponding to the other configured bandwidth parts than thepre-selected one for the UE performing handover. As a result, more freeRACH resources become available for other UEs in the target cell.

In a further exemplary extension of this implementation, the handoverrequest message additionally includes information regarding the state ofthe activated bandwidth part in the source gNB. Alternatively or inaddition, the handover request message includes information regardingdata traffic information predicted by the source gNB, e.g., data trafficto be expected after handover.

For example, the state of the activated bandwidth part may include adescriptor, e.g., to narrow- or wideband, or include a reference to the(band-) width (e.g., in physical resource blocks) of the bandwidth partactivated in the source gNB before handover. Also for example, thetraffic information predicted by the source gNB may include an index tobuffer size levels of buffer statuses in the downlink or includeinformation from buffer status reports from the UE in the uplink beforehandover.

In both cases, when the source gNB forwarding this information in thehandover request message to the target gNB, the target gNB can(actively) select which one of the configured bandwidth parts is bestsuited to become the pre-selected one of the configured bandwidth parts.

For example, if UE traffic demand is low or none, it may be better toactivate the narrower bandwidth part during and after the handover, tomake sure that UE power is not wasted. On the other hand, if UE trafficdemand is high, it would be a wise decision to activate a widerbandwidth part among the configured ones even during the handover.

Then after handover, UE data can be served immediately with widerbandwidth part (with full capacity) without the need of an additionalbandwidth part switching (and hence avoid the delay introduced bybandwidth part switching).

One can argue that during handover there is only a small amount oftraffic to communicate between UE and the target base station, e.g., toperform random access.

Therefore, during handover, UE can operate in narrower bandwidth part.Then after random access is completed, target gNB can indicate UE toswitch to wide BWP if necessary by DCI. However, the following drawbacksare observed:

-   -   Although BWP switching transition time is still under        discussion, it is likely at least one slot (of 15 kHz SCS) is        needed. Therefore, if BWP switching DCI is transmitted in slot n        and then UE performs BWP switching in slot n+1 (since BWP        switching DCI with null data scheduling is not supported UE        still needs to receive PDSCH in narrow BWP in slot n), the first        opportunity to schedule UE data in wide BWP is slot n+2. If UE        traffic demand is high, the latency for data delivery is        compromised.    -   Furthermore, the channel state information (CSI) is also        delayed. Since CSI is measured within the active BWP, CSI for        wide BWP is not available until wide BWP is activated.        Therefore, in the above example where wide BWP is activated in        slot n+2, gNB has to use conservative scheduling decision for at        least slot n+2 (and possibly also slot n+3 if the UE is not able        to feedback CSI in the same slot), resulting in further latency.    -   There is a risk that DCI for BWP switching is missed by the UE.        Although this is related to general DCI error case, it is more        reasonable to avoid the unnecessary BWP switching by setting the        BWP consistently during and after handover.

For conveying this selection of the pre-selected bandwidth part to theUE, the target gNB then (re-)arranges the information regarding theconfigured bandwidth parts in the specific sequence. For example, thetarget gNB can (re-)arrange the best suited one of the configuredbandwidth parts to be the first or the last of the configured bandwidthparts in the specific sequence included in the handover (request)acknowledge message. Then, when the UE is expected to activate, as thepre-selected bandwidth part, (always) the first or last of the specificsequence of bandwidth parts, it will (automatically) activate the bestsuited bandwidth part.

FIG. 5 illustrates a sequence diagram of a handover procedure accordingto a different exemplary implementation of the first embodiment in a3GPP NR deployment scenario. As this different exemplary implementationis closely related to the previous described exemplary implementationshown in FIG. 4 , the following discussion will focus on the differencesonly.

Similarly with before, also here the information on the (appropriatenumber of) configured bandwidth parts, puts the UE in a situation whereit can perform a handover to the target gNB utilizing bandwidth partswhich have been configured for the UE. Accordingly, same or similaradvantages are realized.

Different from the above, there is an index (or bandwidth part index)additionally included in the handover (request) acknowledge message (seemessage 2—FIG. 5 ) from the target gNB to the source gNB andadditionally included in the handover command message (see message3—FIG. 5 ) from the source gNB to the UE. This index indicates which oneof the configured bandwidth parts is to be activated in uplink anddownlink.

For example, both messages may include an index, e.g., BWP #1, for theuplink and downlink, so as to unambiguously indicate which one fromamong the information regarding the configured bandwidth parts is to beactivated. Thus, with the index the according bandwidth part to beactivated can also be pre-selected by the target gNB.

Considering both messages include information regarding a configuredfirst and second bandwidth part. Then, an index indicating the first orthe second configured bandwidth part, regarding which information istransmitted, enables the UE to activate the accordingly pre-selected oneof the two bandwidth parts.

Thereby, it is no longer necessary provide the information regarding theconfigured bandwidth parts in a specific sequence, but rather can theinformation be arranged in an increasing order, e.g., resulting in thenarrow(est) bandwidth part first and the wide(r) bandwidth partthereafter.

Similarly to the further exemplary extension where the request messageadditionally includes information regarding the state of the activatedbandwidth part in the source gNB, or regarding data traffic informationpredicted by the source gNB, e.g., data traffic to be expected afterhandover.

In both cases, when the source gNB forwarding this information in thehandover request message to the target gNB, the target gNB can also here(actively) select which one of the configured bandwidth parts is bestsuited to become the pre-selected one of the configured bandwidth parts.For conveying this selection of the pre-selected bandwidth part to theUE, the target gNB then incorporates an according index to theinformation regarding the configured bandwidth parts in the message asdiscussed before.

FIG. 6 depicts a sequence diagram of a handover procedure according toan exemplary implementation of the second embodiment in a 3GPP NRdeployment scenario. In particular, a user equipment, UE, is shown whenperforming a handover from a source gNB, to a target gNB.

In preparation of the handover, the source gNB transmits a handoverrequest message (see message 1 in FIG. 6 ) to the target gNB. Thehandover request message is again usually transmitted of the Xninterface establishing communication between gNBs in the nextgeneration, NG, radio access network, RAN if such link is availableotherwise the message will be sent via core network. This handoverrequest message provides sufficient details for the target gNB toprepare for the handover of the UE, e.g., perform admission control.

Via this handover request message, the target gNB receives informationregarding the capability of the UE to communicate over at least twobandwidth parts in uplink and downlink. This enables the target gNB toconfigure an appropriate number of bandwidth parts for the UE, e.g.,that meet the capabilities of the UE. For example, if the UE is capableof communicating over two, a narrow and a wide bandwidth part, thetarget gNB does well in configuring also two bandwidth parts for the UE.

Having configured the appropriate number of bandwidth parts in theuplink and downlink, the target gNB includes information thereon in thehandover (request) acknowledge message (see message 2 in FIG. 6 ). Thismessage is transmitted from the target gNB to the source gNB. Thehandover (request) acknowledge message is usually also transmitted overthe Xn interface if possible.

Different from the above, the target gNB also includes in the handover(request) acknowledge message an association table which associates eachof the configured two bandwidth parts with different random accesstransmission parameters.

An example of such an association table is shown in FIG. 7 . Thisexample assumes that at least two bandwidth parts are configured in theuplink and in the downlink, respectively identified UL BWP #0 and UL BWP#1 or DL BWP #0 and DL BWP #1. The possibility of having furtherconfigured bandwidth parts included is hinted at by the extra columnwith three dots.

From this table, it can be seen that each of the configured bandwidthparts in the uplink as well as in the downlink are associated withdifferent transmission parameters.

For example, the configured UL BWP #0 is associated some random accesstransmission parameters, namely either RACH #0 or RACH #2, the furtherconfigured UL BWP #1 is associated with different random accesstransmission parameters, namely either RACH #1 or RACH #3. Equally, theconfigure DL BWP #0 and BWP #1 are also associated with different randomaccess transmission parameters.

It shall not go without saying that each of the configured bandwidthparts in uplink as well as in the downlink are individually (asdiscussed before) associated with different random access parameters butare also in combination associated with different random accessparameters.

In other words, here the combination of each of the configured bandwidthparts in the uplink and in the downlink is also associated withdifferent random access transmission parameters. For example, thecombination of DL BWP #0 and UL BWP #0 is associated with parameter RACH#0 whereas the different combination of DL BWP #0 and UL BWP #1 isassociated with parameter RACH #1.

Despite being beneficial, this is, however, not necessary for achievingadvantageous effects, as will become apparent from the following.

Successively, the source gNB relays the information in a handovercommand message (see message 3 in FIG. 6 ) to the UE. Thus, theinformation regarding the configured bandwidth parts in appropriatenumber is received by the UE. Similar to case described in FIG. 4 , theinformation on configured bandwidth parts alleviates congestion effectson (common) initial bandwidth part during handover, while at the sametime dispensing with the necessity of configuring bandwidth parts at alater point in time.

The source gNB also relays the association table in the handover commandmessage to the UE. This association table enables the UE to perform arandom access channel (RACH) based handover to the target gNB. Bothcontention-based and contention-free random access can perform,depending on whether contention-based or contention-free RACH resourcesthat the target gNB decides to put in the association table.

The UE with the target gNB can perform the random access messagetransmissions, in the RACH-based handover, over the configured bandwidthparts without necessity to rely on the (common) initial bandwidth partonly.

Specifically, with the configured bandwidth parts, there is lesscongestion for the RACH message 1 in the uplink, and the RACH message 2can be more flexibly scheduled in the downlink.

The UE concludes the handover by transmitting a handover completemessage (see message 6—FIG. 6 ) to the target gNB.

Having elaborated on the different configurations of bandwidth parts foran UE, it is also necessary to establish a common understanding betweenthe target gNB and UE which one of the two configured bandwidth parts inboth the uplink and downlink is to be activated.

In this exemplary implementation, it is assumed that the UE (actively)selects the configured bandwidth part to be activated. In other words,here the UE is put in a situation where it is not bound by anypre-selection carried out by the target gNB but it can (freely) selectany of the configured bandwidth parts regarding which information isrelayed from the target gNB.

Advantageously, the UE is generally the best to know about and topredict its own uplink traffic. Despite the fact that buffer statusreports are signaled from the UE to the source gNB, this is notnecessarily accounted for at the target gNB during handover.Furthermore, it can be outdated due to the time gap between the bufferstatus is reported and the handover command is received by the UE. Thus,with the UE (actively) selecting the configure bandwidth part to beactivated, it can be ensured that—at least in the uplink—the activationsuits best the UE's demands during and after the handover.

Having selected one of the configured bandwidth parts, the UE performs aRACH based handover by first activating the selected one bandwidth partand then performing a random access message transmission using theparameters associated with the selected and activated one bandwidthpart.

The random access message transmission not only uses the associatedparameters but also is carried out over the selected and activatedbandwidth part. Thus, there is an unambiguous association between theparameters of the transmission and the bandwidth part over which thetransmission is carried out. This provides the following advantages.

For example, assuming that a UE selects and activates the UL BWP #1,then the association table in FIG. 7 requires it to use the parameterRACH #1 or RACH #3. Either way, when the UE performs the random accessmessage transmission with parameter RACH #1 or RACH #3 the target gNBcan re-assure itself that the random access transmission was effectedover the (correct) UL BWP #1.

This level of re-assurance is beneficial. The random access transmissiondoes not occupy the complete uplink bandwidth part, thus, making itdifficult for the target gNB to tell apart different uplink bandwidthparts, particularly where, for example, the two configured uplinkbandwidth parts are centrally aligned with each other or are configurewith a substantial overlap.

Accordingly, the association table prevents from situations in which thetarget gNB receives a random access message transmission, but cannotdetermine which uplink bandwidth part was used, and thus has beenselected and activated by the UE.

Additionally, the parameters from the association table in FIG. 7 alsoconvey information regarding the selected and activated downlink part.For example, when the UE performs the random access message transmissionwith the parameter RACH #1, then the target gNB knows not only that theUL BWP #1 but also the DL BWP #0 was selected.

Accordingly, the association table can assist the UE and gNB to arriveat a common understanding which of the configured bandwidth parts the UEhas selected and activated in the uplink and in the downlink for use incommunications (already) part of the handover procedure.

Referring now to the RACH based handover in further detail. On the basisof the information in the handover command, the UE selects and activatesone of the configured bandwidth parts in the uplink and downlink. Thesebandwidth parts are used in the subsequent handover procedure.

The UE transmits a random access preamble message (see message 4—FIG. 6) to the target gNB with a preamble sequence and/or time and frequencyresources from the association table corresponding to the selected andactivated bandwidth.

This random access preamble message is received at the target gNB andresponded to with a random access response message (see message 5—FIG. 6). This message is transmitted from the target gNB to the UE. The targetgNB uses for transmission of this message the corresponding bandwidthpart in the downlink.

When coming back to the example with random access transmissionparameter being RACH #1, then the target gNB uses for the transmissionof the random access response message the downlink bandwidth part DL BWP#0. Again it can be appreciated that the association table achieves acommon understanding between the UE and the target gNB which one of theconfigure bandwidth parts are to be used during and after handover.

There may, however, be situations where this level of autonomy at the UEis undesired, or even disadvantageous.

In an exemplary extension of this implementation, thus, the handover(response) acknowledge includes a bandwidth part index which will beforwarded to UE in handover command which restricts the freedom for theUE to select the bandwidth parts. Accordingly, the UE receivesinformation regarding configured bandwidth parts from among which itcan, however, only select that one which correspond to the index. Therestriction can also be imposed by the source gNB in the handovercommand. In such case, the bandwidth part index is determined by thesource gNB.

A particular advantageous effect is attained when this index indexes aspecific downlink bandwidth part to be used while, at the same timeretains the freedom for the UE to (actively) select its uplink bandwidthpart for handover. Then, the index indexes a subset of bandwidth partcombinations, namely uplink bandwidth parts for that specific downlinkbandwidth part which correspond to the bandwidth part index.

With such a definition of the bandwidth part index, the UE is restrictedto select and activate bandwidth parts from a subset of all theconfigured bandwidth parts regarding which the information is includedin the handover command. This subset includes all configured uplinkbandwidth parts but none of the configured downlink bandwidth parts, asthe downlink bandwidth part is pre-selected by the index.

The advantageous effect results from the observation that the UE isgenerally the best to know about and to predict its own uplink traffic,whereas the source gNB or target gNB can do its best to predict thedownlink traffic. In other words, this index mediates between twoextremes, namely one extreme where the target gNB pre-selects allbandwidth parts, and another extreme where the UE selects all bandwidthparts.

This exemplary extension of having the index results in furtheradvantages when combined with the following modifications.

In a further exemplary extension of this implementation, the handoverrequest message additionally includes information regarding the state ofthe activated bandwidth part in the source gNB. Alternatively or inaddition the handover request message includes information regardingdata traffic information predicted by the source gNB, e.g., data trafficto be expected after handover.

In both cases, when forwarding this information in the handover requestmessage to the target gNB, it can (actively) select which one of theconfigured bandwidth parts is best suited to become the pre-selecteddownlink bandwidth part without restricting the UE's freedom to(actively) select an uplink bandwidth part from the configured bandwidthparts.

For conveying this selection of the pre-selected downlink bandwidth partto the UE, the target gNB includes a corresponding index (bandwidth partindex) in the handover (request) acknowledge message, which is relayedby the source gNB in form of the handover command to the UE.

Then, when the UE is expected to select and activate the configuredbandwidth parts, it restricted to do so from the subset of all theconfigured bandwidth parts regarding which the information is includedin the handover command. Thereby, the UE cannot only (actively) selectthe best uplink bandwidth part but also receive guidance when selectingthe best downlink bandwidth part.

It goes without saying that the association table permits the target gNBto gain the level of re-assurance regarding which one of the configureduplink bandwidth parts has been selected and activated by the UE.

In a different exemplary extension of this implementation, the bandwidthpart index included in the handover (request) acknowledge message andthe handover command indexes a single one bandwidth part in the uplinkas well as in the downlink. Thereby, the UE is deprived of the freedomto select any one of the configured bandwidth part, neither in thedownlink nor in the uplink.

Coming back to the more general discussion of the exemplaryimplementation, it must be mentioned that the target gNB does not knowthe UE selected one of the configured bandwidth parts in advance beforeUE makes the first contact with the target gNB by sending RACH message1. In other words, the UE is given truly given the freedom to select and(at the same time) activate the (best suited) one of the configuredbandwidth parts (at least for uplink).

As the random access transmission message (see message 4—FIG. 6 ) isalready transmitted over the UE selected uplink bandwidth part, thetarget gNB has to make arrangements to receive this message regardlessof what the outcome of the selection may be. This uncertainty brings thetarget gNB into a situation where it cannot foresee the uplink bandwidthpart to be used.

For this reasons, the target gNB activates not only one but instead allof the configured bandwidth parts, e.g., all uplink bandwidth partsregarding which information was included in the handover (request)acknowledge and handover command message. In other words, different fromthe previous implementation, the target gNB must monitor not one but allconfigured uplink bandwidth parts.

Nevertheless, once the association table gives away which one of theconfigured bandwidth parts was selected, the uncertainty is removed fromthe target gNB and it can proceed with de-activating all non-selectedbandwidth parts.

Coming back the example where the UE has selected RACH #1 for use withthe random access preamble transmission (message 4—FIG. 6 ). Due to theuncertainty, the target gNB has to activate UL BWP #0 and UL BWP #1which has (previously) configured and indicated in form of additionalinformation to the UE. Only then does the target gNB ensure that itreceives the message regardless of what the selection may be.

With the reception of this random access preamble transmission with RACH#1, the target gNB is provided with the knowledge on the outcome of theUE's selection, e.g., it knows that the UE has selected DL BWP #0 and ULBWP #1 as shown in FIG. 7 . The, the target gNB can instantly proceedwith deactivating the remaining of the configured but non-selected.

FIG. 8 illustrates a sequence diagram of a handover procedure accordingto a different exemplary implementation of the second embodiment in a3GPP NR deployment scenario. As this different exemplary implementationis closely related to the previous described exemplary implementationshown in FIG. 6 , the following discussion will focus on the differencesonly.

As starting point, this implementation is based on the understandingthat handovers do not necessarily require RACH transmissions (termedRACH-based handover) but instead that handovers are also conceivable ina RACH-less fashion (termed: RACH-less handovers).

Such RACH-less handovers are, for example, envisioned in mobilecommunication systems where there is time synchronization betweenmultiple gNB s or the time advance regarding the neighboring cell isalready known to the UE performing handover (e.g., when the secondarycell (SCell) is changed to the primary cell (PCell)). In such cases, theUE is not required to perform random access procedure forre-establishing time synchronization when performing handover from asource to a target cell.

For example, the UE would with such a RACH-less handover re-use the sametiming advance command when communicating with the source gNB or withthe target gNB. There is simply not necessity to perform a random accesstransmission, e.g., random access preamble transmission, when there isno uncertainty in the timing in the target gNB.

With this understanding, it is immediately evident that an associationtable associating the configured bandwidth parts with different randomaccess transmission parameters is useless. Rather, in this exemplaryimplementation there is an association table which associates theconfigured bandwidth parts with different uplink shared channeltransmission parameters as shown in FIG. 9 .

For example, the different uplink shared channel transmission parametersmay include time and frequency of radio channel resources, which can beused by the UE when transmitting the handover complete message (seemessage 4—FIG. 8 ). In other words, the uplink shared channeltransmission parameters could be considered as being uplink grants todifferent radio resources in the physical uplink shared channel of thetarget base station.

Aside of this fundamental difference, the handover procedure onlydiffers with regard to the information included in the handover(request) acknowledge message (see message 2—FIG. 8 ) and included inthe handover command message (see message 3—FIG. 8 ) transmitted fromthe target gNB via the source gNB to the UE.

These messages do not include an association table associating theconfigured bandwidth parts with different random access transmissionparameters, but instead include an association table associating theconfigured bandwidth parts with different uplink shared channeltransmission parameters.

With the different uplink shared channel transmission parameters, thetarget gNB also here gains a beneficial level of re-assurance. As thehandover complete transmission does not occupy the complete uplinkbandwidth part, the target gNB will have difficulties to tell apart thedifferent uplink bandwidth parts, particularly where, for example, twoconfigured uplink bandwidth parts are centrally aligned with each other,or are configured with substantial overlap.

Consequently, also here the association table advantageously preventsfrom situations in which the target gNB receives an uplink sharedchannel transmission, but cannot determine which uplink bandwidth partwas used, and thus has been selected and activated by the UE. For theremaining details, reference is made to the above description of FIG. 6which can be understood as describing the procedure as well as theadvantages in analogous form.

It shall be mentioned that in case of carrier aggregation where multiplecomponent carriers are configured for the UE, the bandwidth partconfiguration and activation method in this disclosure is for eachcomponent carrier. In other words, each component carrier hasindependent bandwidth part configurations. During handover, UE's PCellwill be changed. However, UE SCell configurations can be either bereleased or still kept, depending on the handover acknowledge receivedby the UE. Similarly, the new bandwidth part configurations can beprovided accordingly.

Referring now to the most general description, it can be summarized thatthe present disclosure provides for mechanisms which permit acoordinated configuration of bandwidth parts at handover, therebyminimizing interruption time and reducing the power consumption athandover. Figuratively speaking, if the utilization level of the targetbase station permits, the bandwidth parts can be configured same insource and target cell as discussed with regard to in FIG. 2B.

This is particularly so if the handover request message (see message1—FIGS. 4, 5, 6, and 8 ) additionally includes information regarding atleast a third and a different fourth bandwidth part which are configuredin the source base station and/or information regarding the activatedone of the configured at least third and fourth bandwidth part in thesource base station.

Then the target base station can configuring for the mobile terminal thefirst bandwidth part and the second bandwidth part in the transceiverbased on the third bandwidth part and fourth bandwidth part,respectively. More specifically, the target base station can configurethe first bandwidth part same (or similar) as the third bandwidth partand the second bandwidth part same (or similar) as the fourth bandwidthpart.

Thus, a coordinated configuration of the bandwidth parts is achieved athandover realizing the numerous advantages discussed above.

Finally, when having the information regarding the most recentlyactivated bandwidth part in the source base station readily available inthe target base station, then this target base station can not onlycoordinately configure the bandwidth parts for the mobile terminal, butit can also transmit the handover request acknowledge message includinga bandwidth part index, where the bandwidth part index indexes thatbandwidth part which is the same as the previously activated one of theconfigured bandwidth part in the source base station.

The present disclosure can be realized by software, hardware, orsoftware in cooperation with hardware. Each functional block used in thedescription of each embodiment described above can be partly or entirelyrealized by an LSI such as an integrated circuit, and each processdescribed in the each embodiment may be controlled partly or entirely bythe same LSI or a combination of LSIs. The LSI may be individuallyformed as chips, or one chip may be formed so as to include a part orall of the functional blocks. The LSI may include a data input andoutput coupled thereto. The LSI here may be referred to as an IC, asystem LSI, a super LSI, or an ultra LSI depending on a difference inthe degree of integration.

However, the technique of implementing an integrated circuit is notlimited to the LSI and may be realized by using a dedicated circuit, ageneral-purpose processor, or a special-purpose processor. In addition,a FPGA (Field Programmable Gate Array) that can be programmed after themanufacture of the LSI or a reconfigurable processor in which theconnections and the settings of circuit cells disposed inside the LSIcan be reconfigured may be used. The present disclosure can be realizedas digital processing or analogue processing. If future integratedcircuit technology replaces LSIs as a result of the advancement ofsemiconductor technology or other derivative technology, the functionalblocks could be integrated using the future integrated circuittechnology. Biotechnology can also be applied.

According to a first aspect, a mobile terminal is suggested forperforming a handover procedure in a mobile communication system from asource base station to a target base station. The target base station isconfigured for the mobile terminal with at least a first bandwidth partand a different second bandwidth part within its cell bandwidth. Themobile terminal comprises: a transceiver which, in operation, receivesfrom the source base station a handover command message includinginformation regarding the configured at least first bandwidth part andsecond bandwidth part; and a processor which, in operation and uponreception of the handover command message, activates in the transceiverat least a pre-selected one of the configured at least first bandwidthpart or second bandwidth part, and controls the transceiver to perform,over the activated at least one of the configured at least firstbandwidth part or second bandwidth part, communication with the targetbase station as part of the handover procedure.

According to a second aspect, which can be combined with the firstaspect, the information regarding the configured at least firstbandwidth part and second bandwidth part has a specific sequence, andthe processor, in operation, activates, as the pre-selected one of thebandwidth parts, the first or last or a specific other one, if more thanthe at least first bandwidth part and the second bandwidth part areconfigured, in the specific sequence.

According to a third aspect, which can be combined with the firstaspect, the received handover command message additionally includes abandwidth part index, and the processor activates the pre-selected oneof the configured at least first bandwidth part or the second bandwidthpart which corresponds to the bandwidth part index.

According to a fourth aspect, which can be combined with the first tothird aspect, the processor controls the transceiver to perform at leasta random access message transmission to the target base station as partof the handover procedure.

According to a fifth aspect, which can be combined with the first tofourth aspect, in case the received handover command messageadditionally includes a plurality of different random accesstransmission parameters associated with at least the pre-selected one ofthe configured at least first bandwidth part and second bandwidth part,the processor controls the transceiver to perform at least a randomaccess message transmission to the target base station using the randomaccess transmission parameters associated to the activated pre-selectedone of the configured at least first bandwidth part or the secondbandwidth part.

According to a sixth aspect, a mobile terminal is proposed forperforming a handover procedure in a mobile communication system from asource base station to a target base station. The target base station isconfigured for the mobile terminal with at least a first bandwidth partand a different second bandwidth part within its cell bandwidth. Themobile terminal comprises: a transceiver which, in operation, receivesfrom the source base station a handover command message includinginformation regarding the configured at least first bandwidth part andsecond bandwidth part; and a processor which, in operation and uponreception of the handover command message, selects and activates in thetransceiver at least one of the configured at least first bandwidth partor the second bandwidth part, and controls the transceiver to perform,over the selected and activated at least one of the configured at leastfirst bandwidth part or the second bandwidth part, communication withthe target base station as part of the handover procedure.

According to a seventh aspect, which can be combined with the sixthaspect, the received handover command message additionally includes abandwidth part index, and the processor, in operation, selects andactivates, in the transceiver, one of a subset of the configured atleast first bandwidth part or the second bandwidth part whichcorresponds to the bandwidth part index.

According to an eight aspect, which can be combined with the sixthaspect, the bandwidth part index indexes a subset of uplink bandwidthparts for a specific downlink bandwidth part, and the processor, inoperation, selects and activates, in the transceiver, the subset of theconfigured at least first bandwidth part or the second bandwidth partwhich corresponds to the bandwidth part index.

According to a ninth aspect, which can be combined with the sixth toeight aspect, the received handover command message additionallyincludes: a plurality of different random access transmission parametersassociated with each or a subset of the configured at least firstbandwidth part and second bandwidth part; and the processor, inoperation, controls the transceiver to perform at least a random accessmessage transmission using the random access transmission parametersassociated to the selected and activated one of the configured at leastfirst bandwidth part or the second bandwidth part.

According to the tenth aspect, which can be combined with the ninthaspect, the plurality of random access transmission parameters compriseat least one or more of:—a random access preamble sequence, transmittedwith the random access message, and—time and frequency of radio channelresources, to be used by the mobile terminal when transmitting therandom access message to the target base station.

According to an eleventh aspect, a target base station is suggested forperforming a handover procedure of a mobile terminal in a mobilecommunication system from a source base station. The target base stationis capable of communicating with the mobile terminal over each of atleast a first bandwidth part and a different second bandwidth partwithin its cell bandwidth. The target base station comprises: atransceiver which, in operation, receives from the source base station ahandover request message including information regarding the capabilityof the mobile terminal to communicate over at least the first bandwidthpart and second bandwidth part; and a processor which, in operation andupon reception of the handover request message, controls the transceiverto configure for the mobile terminal at least the first bandwidth partand the second bandwidth part, and controls the transceiver to transmitsto the source base station a handover request acknowledge message,wherein the handover request acknowledge message includes informationregarding the configured at least first bandwidth part and secondbandwidth part.

According to a twelfth aspect, which can be combined with the eleventhaspect, the processor, in operation and after controlling thetransmitter to transmit the handover request acknowledge message,activates in the transmitter the same pre-selected one of the configuredat least first bandwidth part or second bandwidth part which the mobileterminal is expected to activate.

According to a thirteenth aspect, which can be combined with the twelfthaspect, the information regarding the configured at least firstbandwidth part and second bandwidth part has a specific sequence, andthe processor, in operation, activates, as the pre-selected one of thebandwidth parts, the first or last or a specific other one, if more thanthe at least first bandwidth part and the second bandwidth part areconfigured, in the specific sequence.

According to a fourteenth aspect, which can be combined with the twelfthaspect, the handover request acknowledge message additionally includes abandwidth part index, and the processor, in operation, activates thepre-selected one of the configured at least first bandwidth part or thesecond bandwidth part which corresponds to the bandwidth part index.

According to a fifteenth aspect, which can be combined with the eleventhto fourteenth aspect, the handover request message additionally includesinformation regarding the state of the activated bandwidth part orpredicted traffic information; and the processer, in operation and uponreception of the handover request message, controls the transceiver toselect and activate at least one the at least the first bandwidth partand the second bandwidth part which the mobile terminal, as part of thehandover procedure, is expected to activate as the pre-selectedbandwidth part.

According to a sixteenth aspect, which can be combined with the eleventhaspect, the processor, in operation and after controlling thetransmitter to transmit the handover request acknowledge message,activates in the transceiver all of the configured at least firstbandwidth part or second bandwidth part.

According to an seventeenth aspect, which can be combined with theeleventh aspect, the handover request acknowledge message additionallyincludes:—a plurality of different uplink shared channel transmissionparameters, each associated with a different one of the configured atleast first bandwidth part and second bandwidth part; and the processor,in operation, controls the transceiver to schedule candidates ofhandover complete message transmission using all of the plurality ofuplink shared channel transmission parameters which are associated withthe configured at least first bandwidth part or the second bandwidthpart.

According to an eighteenth aspect, which can be combined with theseventeenth aspect, the plurality of uplink shared channel transmissionparameters comprise—time and frequency of radio channel resources, to beused by the mobile terminal when transmitting the handover completemessage to the target base station.

According to a nineteenth aspect, which can be combined with theseventeenth or eighteenth aspect, in case the handover requestacknowledge message additionally includes a plurality of uplink sharedchannel transmission parameters, each associated with a different one ofthe configured at least first bandwidth part and second bandwidth part,the transceiver, in operation, additionally receives from the mobileterminal a handover complete message transmission using one of theplurality of uplink shared channel transmission parameters which isassociated to the by the mobile terminal selected and activated of theconfigured at least first bandwidth part or the second bandwidth part;and the processor, in operation, deactivates the remaining of theconfigured at least first bandwidth part and second bandwidth part whichthe mobile terminal has not selected and activated.

According to a twentieth aspect, which can be combined with the eleventhaspect, the handover request acknowledge message additionallyincludes:—a plurality of different random access transmission parameterseach associated with a different one of the configured at least firstbandwidth part and second bandwidth part; and the processor controls thetransceiver to reserve random access message transmissions using all ofthe plurality of random access transmission parameters which areassociated to the configured at least first bandwidth part or the secondbandwidth part.

According to a twenty-first aspect, which can be combined with thetwentieth aspect, the plurality of random access transmission parameterscomprise at least one or more of:—a random access preamble sequence,transmitted with the random access message,—time and frequency of radiochannel resources, to be used by the mobile terminal when transmittingthe random access message to the target base station.

According to a twenty-second aspect, which can be combined with thetwenty-first aspect, in case the handover request acknowledge messageadditionally includes a plurality of different random accesstransmission parameters each associated with a different one of theconfigured at least first bandwidth part and second bandwidth part, thetransceiver, in operation, additionally receives from the mobileterminal a random access message transmission using one of the pluralityof random access transmission parameters which is associated to the bythe mobile terminal selected and activated of the configured at leastfirst bandwidth part or the second bandwidth part; and the processor, inoperation, deactivates the remaining of the configured at least firstbandwidth part and second bandwidth part which the mobile terminal hasnot selected and activated.

According to a twenty-third aspect, which can be combined with theeleventh aspect, the handover request message additionallyincludes:—information regarding at least a third bandwidth part and adifferent fourth bandwidth part which are configured for the mobileterminal in the source base station.

According to a twenty-fourth aspect, which can be combined with thetwenty-third aspect, the handover request message additionallyincludes:—information regarding the activated one of the configured atleast third bandwidth part and fourth bandwidth part in the source basestation.

According to a twenty-fifth aspect, which can be combined with thetwenty-fourth aspect, the processor, in operation, configures, for themobile terminal, the first bandwidth part and the second bandwidth part,in the transceiver, based on the third bandwidth part and fourthbandwidth part, respectively.

According to a twenty-sixth aspect, which can be combined with thetwenty-fifth aspect, the processor, in operation, controls thetransceiver to transmit the handover request acknowledge messageincluding a bandwidth part index, and the bandwidth part index indicatesthat bandwidth part which is the same as the previously activated one ofthe configured at least third bandwidth part and fourth bandwidth partin the source base station.

According to a twenty-seventh aspect, a method is proposed forperforming a handover procedure of a mobile terminal in a mobilecommunication system from a source base station to a target basestation. The target base station is configured for the mobile terminalwith at least a first bandwidth part and a different second bandwidthpart within its cell bandwidth. The method comprises the steps of:receiving from the source base station a handover command messageincluding information regarding the configured at least first bandwidthpart and second bandwidth part; and upon reception of the handovercommand message, activating at least a pre-selected one of theconfigured at least first bandwidth part or second bandwidth part, andcommunicating, over the activated at least one of the configured atleast first bandwidth part or second bandwidth part, with the targetbase station as part of the handover procedure.

According to a twenty-eighth aspect, a method is suggested forperforming a handover procedure of a mobile terminal in a mobilecommunication system from a source base station to a target basestation. The target base station is configured for the mobile terminalwith at least a first bandwidth part and a different second bandwidthpart within its cell bandwidth. The method comprises the steps of:receiving from the source base station a handover command messageincluding information regarding the configured at least first bandwidthpart and second bandwidth part; and upon reception of the handovercommand message, selecting and activating at least one of the configuredat least first bandwidth part or the second bandwidth part, andcommunicating, over the selected and activated at least one of theconfigured at least first bandwidth part or the second bandwidth part,with the target base station as part of the handover procedure.

According to a twenty-ninth aspect, a method is proposed for a targetbase station to perform a handover procedure of a mobile terminal in amobile communication system from a source base station The target basestation being capable of communicating with the mobile terminal overeach of at least a first bandwidth part and a different second bandwidthpart within its cell bandwidth. The method comprises the steps of:receiving from the source base station a handover request messageincluding information regarding the capability of the mobile terminal tocommunicate over at least the first bandwidth part and second bandwidthpart; and upon reception of the handover request message, configuringfor the mobile terminal at least the first bandwidth part and the secondbandwidth part, and transmitting to the source base station a handoverrequest acknowledge message, wherein the handover request acknowledgemessage includes information regarding the configured at least firstbandwidth part and second bandwidth part.

The various embodiments described above can be combined to providefurther embodiments. All of the U.S. patents, U.S. patent applicationpublications, U.S. patent applications, foreign patents, foreign patentapplications and non-patent publications referred to in thisspecification and/or listed in the Application Data Sheet areincorporated herein by reference, in their entirety. Aspects of theembodiments can be modified, if necessary to employ concepts of thevarious patents, applications and publications to provide yet furtherembodiments.

These and other changes can be made to the embodiments in light of theabove-detailed description. In general, in the following claims, theterms used should not be construed to limit the claims to the specificembodiments disclosed in the specification and the claims, but should beconstrued to include all possible embodiments along with the full scopeof equivalents to which such claims are entitled. Accordingly, theclaims are not limited by the disclosure.

1. An integrated circuit for controlling a target base station toperform a handover procedure of a user equipment from a source basestation, the integrated circuit comprising: transceiver circuitry,which, in operation, receives from the source base station a handoverrequest message which includes a traffic status of the user equipmentand which includes information regarding the user equipment's capabilityto communicate with the target base station over a first bandwidth partand a second bandwidth part different from the first bandwidth partwithin a cell bandwidth of the target base station; and processingcircuitry, which, in operation and upon reception of the handoverrequest message, selects a bandwidth part index indicative of the firstbandwidth part or the second bandwidth part, controls the transceivercircuitry to configure for the user equipment at least the firstbandwidth part and the second bandwidth part, and controls thetransceiver circuitry to transmit to the source base station a handoverrequest acknowledge message, wherein the handover request acknowledgemessage includes information regarding the configured at least firstbandwidth part and second bandwidth part which includes the selectedbandwidth part index; wherein the bandwidth part index received by thesource base station is transmitted in a handover command message fromthe source base station to the user equipment to activate the firstbandwidth part or the second bandwidth part corresponding to thebandwidth part index, and wherein the handover command message includesa specific sequence of information, and the bandwidth part index toactivate the first bandwidth part or the second bandwidth part isincluded at a specific position in the specific sequence.
 2. Theintegrated circuit according to claim 1, wherein the processingcircuitry, in operation and after controlling the transceiver circuitryto transmit the handover request acknowledge message, activates in thetransceiver circuitry the first bandwidth part or the second bandwidthpart corresponding to the selected bandwidth part index.
 3. Theintegrated circuit according to claim 1, wherein the handover requestmessage additionally includes information regarding a state of theactivated bandwidth part or predicted traffic information.
 4. Theintegrated circuit according to claim 1, wherein the processingcircuitry, in operation and after controlling the transceiver circuitryto transmit the handover request acknowledge message, activates in thetransceiver circuitry all of configured bandwidth parts including thefirst bandwidth part and the second bandwidth part.
 5. The integratedcircuit according to claim 1, wherein the handover request acknowledgemessage additionally includes: a plurality of different uplink sharedchannel transmission parameters, each associated with a different one ofconfigured bandwidth parts including at least the first bandwidth partand the second bandwidth part; and the processing circuitry, inoperation, controls the transceiver circuitry to schedule candidates ofhandover complete message transmission using all of the plurality ofuplink shared channel transmission parameters which are associated withthe configured bandwidth parts, wherein the plurality of uplink sharedchannel transmission parameters comprise time and frequency of radiochannel resources, to be used by the user equipment when transmitting ahandover complete message to the target base station; and in case thehandover request acknowledge message additionally includes the pluralityof uplink shared channel transmission parameters, the transceivercircuitry, in operation, additionally receives from the user equipmentthe handover complete message using one of the plurality of uplinkshared channel transmission parameters which is associated with thefirst bandwidth part or the second bandwidth part activated by the userequipment; and the processing circuitry, in operation, deactivates theremaining configured bandwidth parts which the user equipment has notselected and activated.
 6. The integrated circuit according to claim 1,wherein the handover request acknowledge message additionally includes:a plurality of different random access transmission parameters eachassociated with a different one of configured bandwidth parts includingat least the first bandwidth part and the second bandwidth part; and theprocessing circuitry, in operation, controls the transceiver circuitryto reserve random access message transmissions using all of theplurality of random access transmission parameters which are associatedwith the configured bandwidth parts, wherein the plurality of randomaccess transmission parameters comprise at least one or more of: arandom access preamble sequence, or time and frequency of radio channelresources, to be used by the user equipment when transmitting a randomaccess message to the target base station; and in case the handoverrequest acknowledge message additionally includes the plurality ofdifferent random access transmission parameters, the transceivercircuitry, in operation, additionally receives from the user equipmentthe random access message using one of the plurality of random accesstransmission parameters which is associated with the first bandwidthpart or the second bandwidth part selected and activated by the userequipment; and the processing circuitry, in operation, deactivates theremaining configured bandwidth parts which the user equipment has notselected and activated.
 7. The integrated circuit according to claim 1,wherein the handover request message additionally includes: informationregarding at least a third bandwidth part and a different fourthbandwidth part which are configured for the user equipment in the sourcebase station; and information regarding the activated third bandwidthpart or the activated fourth bandwidth part in the source base station;wherein the processing circuitry, in operation, controls the transceivercircuitry to configure, for the user equipment, the first bandwidth partand the second bandwidth part based on the third bandwidth part andfourth bandwidth part, respectively; and the bandwidth part indexindicates the bandwidth part which is the same as the third bandwidthpart or the fourth bandwidth part previously activated in the sourcebase station.